gpg: Regenerate test data for test-gpg-verify-result
authorMatthew Barnes <mbarnes@redhat.com>
Thu, 19 Mar 2015 16:43:04 +0000 (12:43 -0400)
committerMatthew Barnes <mbarnes@redhat.com>
Thu, 19 Mar 2015 16:43:04 +0000 (12:43 -0400)
commitda918a74d5f4e33cddfdd43e465d40d00d6604e0
treec60ba9e8abb519a6de320f009c90ec3256fff970
parentf9e95e2cd39e23b2c420addc10917e8e3d6b7a20
gpg: Regenerate test data for test-gpg-verify-result

Turns out the expired signature case was failing because the signature
itself was corrupted.  Reconstructed the test data and updated the test
code.  Note, an expired signature is still counted as valid.

Also, handy debugging trick for setting a key or signature expiry: the
CLI makes it appear the shortest expiry is 1 day, but it also secretly
recognizes "seconds=N".
tests/gpg-verify-data/lgpl2.sig
tests/gpg-verify-data/pubring.gpg
tests/gpg-verify-data/secring.gpg
tests/gpg-verify-data/trustdb.gpg
tests/test-gpg-verify-result.c